*************************************************** ** NP00602 FILE ** ** DATE = 11/04/96 ** PHONE = 8-444-0017 ** CONTACT = SANDY PETERSON ** C/T = RD0011 ** USER = SANDYPE NODE = RALVM29 ** *************************************************** APARTXT NA01379 = APPN station hangs if it uses a DLSw wan connection that drops while the station is in xid exchange. APARTXT NA01492 = libodm.a (breakcrit), and libcurses have memory leaks exhibited in sy sman. APARTXT NA01102 = PANIC in get_pinned() when out of buffers APARTXT NA01239 = The running of traces (in this case dls traces - haven't seen with others as of yet) causes a system dump in the kernel code which parses the stack. The dump does not happen right away. APARTXT NA01707 = Changes required for Cornell RPQ Integration. APARTXT NA01375 = the protocol information and statistice screen does not format correctly on the interface utilization selection. a lot of empty spaces... APARTXT NA01403 = When using frame relay, and you have configured one or more DLCIs you sometimes have to configure those dlcis for all other protocols on that port. This fixes that problem. APARTXT NA01868 = mondisk:shrink_file gets read of len 0, causes 100%cpu. APARTXT NA01416 = DLS bringing up connection sends out a sabme to the server. DLS waits 1.2 seconds and sends out another sabme, but the server has already started to respond to the first sabme. The UA for the first sabme comes in, we then send out rnr, the respo nse for the second sabme comes in (UA), the dls llc code issues a disconnect and he takes the session down. APARTXT NA01598 = Customers need to be able to control their queue depth. APARTXT NA01511 = Logical interfaces are not deleted when the corresponding kernel ifaddr is deleted. STOP_SYMPTOM APARTXT NA01581 = The Line Utilization counter in sysman/operations/ Network Statistics was not operating correctly, it was showing a much higher number than expected, like 3000%. APARTXT NA01599 = SR ARB -> TB conversion on serial and TR adapters is not working properly. In such a configuration all ARB traffic sent to the TB Serial card will be dropped. Bridge Trace will only show reciept of the frame but not translation. APARTXT NA01759 = see above. APARTXT NA01767 = Enhance IP forwarder to support WAN reroute for UPS. When PPP IPCP detects other end down, it will set dest. address of PPP to 0.0.0.0. IP forwadrer code has to deletes default routes created for this interface. It marks the interface down in _interface_info as DOWN. APARTXT NA01672 = Migration to V1R3-NP00383 via update NP99915 fails to apply if any prior PTF has been applied more than once in VPD. For example, an apply/reject/apply sequence of a prior PTF will cause this error (fail of apply in NP99915). APARTXT NA01786 = The symptom is a broad class of adapter problems from hangs to misc data comm problems and incorrect MIB output caused by adapter memory corruption. The frame relay areas are impacted first eventually followed by the entire adapter memory. Frame Relay and IP must be configured on at least one interface on the failing adapter. The root cause is a configuration where the IP addresses that are learned from arps and inarps are GREATER THAN the broadcast address. The work-around is to reconfigure addresses and netmasks on connected dlcis such that all addresses are in the correct subnet. APARTXT NA02270 = GateD doesn't advertise destination PPP address in OSPF when the neighbor PPP not in FULL state. APARTXT NA02069 = Misleading message if you activate something applied on top of the NP00383 level. APARTXT NA02075 = Customers with the backdoor password (UK ISSC and Fuji Bank) can cause core dumps via common typing mistakes. Although these are user errors, this wastes time for PE (who for some reason can't recognize this as a user error) and Development (who must look at the core dumps and error logs). APARTXT NA02086 = Check in for a new tool called ospf_sock. Also take the old tool called ospfconf (nodody used it). APARTXT NA01848 = Customer at V1R2+331 installs NP00336 or V1R3+383, when PU4-PU4 connection is tried, conversation shows connected momentarily and then conversation is dropped and connection INOPs. XID seems to be sent to NCP but get know reply. 6611 does not send some test frames. APARTXT NA02130 = ibmipxAddrAddress not reported correctly APARTXT NA01902 = when loading a UNIX diskette via SYSMGR (for EPTFs), using PF4 to list the contents of diskette results in a hang (processind data ...) is display, diskette is read, and sysmgr waits... APARTXT NA01904 = When a 6611 is configured for translational bridging on an ethernet and more than one token ring, it is possible that routes to token ring stations are incorrectly cached. This can result in ethernet stations being unable to contact stations on the token ring. APARTXT NA01893 = If you commit NP99915 and NP00600 together, you do not get the option to activate any EPTF's after that. Problem can be avoided by committing NP99915 and then committing NP00600. If already into the problem, 6611 PE or Dev. needs to repair faulty condition. Either L. Bouila or Suri needs to fix it. APARTXT NA01933 = On some post 383 levels, periodic reboots with dls and sdlc configured will IPL with a 92c set on the LEDs. APARTXT NA01938 = time change should not restart lnppp bnppp or tra_trsa APARTXT NA02150 = cub stat takes up 100 % of cpu when running APARTXT NA01978 = Disable of 'mpq1' also does 'mpq10-mpq19' APARTXT NA01986 = Virtual link cannot make FULL relationship with destination APARTXT NA02273 = After a dlsw partner wan connection is broken and re-established, the state of the wan connection shown by dlstools wancons is ReqRx. Also possibly a dlsw partner connection will be displayed by dlstools wancons with the send side in state RUNNIN and the receive side in state CLEANSLATE. STOP_SYMPTOM APARTXT NA01991 = LLCoe_saps and sr->tb address mapping are not being configured for adapters that have an interface number greater then 8. For example, if the first 2 slots are dual t1 and the 3rd slot is a 4port t1 adapter and the 4th slot is an ethernet port. The ethernet port will not have LLCoe_saps configured. Use the debugger to dump these bytes and you would see all 16 bytes of zero instead of the default 15 00 00 .... 00 00 45 Also the address mapping database from TR to ENET and back shows all zeros... APARTXT NA02614 = Internal Enhancements for NP00603 APARTXT NA01994 = dls wan hung with write socket in Run'n and read socket Clean on the dls partner that is configured to call out. Work around is to restart dls. APARTXT NA01990 = With SDLC X.21 connections links bounced up/down. With >2 SDLC adapters, 6611 froze. APARTXT NA02000 = DLSw slan write process dumps. pd_dump file is in transfer directory. SDLC link is stuck in disconnect pending state. It appeared that at the same time problems were occurring on the serial interface. APARTXT NA02001 = A hard disk was moved from a 6611-175 to a 6611-145. When SDLC adapters were added, either the adapter numbers or the port numbers were left in a non-increasing sequence. This causes various problems where SDLC doesn't work correctly. APARTXT NA02003 = Internal enhancements APARTXT NA02113 = Internal Enhancements for NP00385 APARTXT NA02164 = up/down status for sdlc interfaces intermittantly incorrect APARTXT NA02114 = when an SDLC station is defined with a destination mac, and the station is contacted, no CURFRAME is wancast. the expected circuit does not come up. APARTXT NA02014 = This is not a bug in base code. It is purely a limitation in original design due to the SRAM constraint on adapter. The limit was 16. Now this will increased to 32. APARTXT NA02030 = DLS ANALYST processs dies. This prevents any further DLS connections from establishing. * This is caused by the ANALYST receiving a GIP message (can-u-reach) with a non zero message length. APARTXT NA02031 = Customer has dual token ring. One port stops transmitting, but is still receiving. Adapter is NOT hung and is NOT marked down (in system connections). The XmitMaxTlistDrop MIB counter is increasing. APARTXT NA02051 = IP translational bridging will hang for a minute or 2 and then recove r Should only happen if you have fx60101 or higher installed was introduced by defect 21071 APARTXT NA02053 = X.25 takes 10 minutes to start link recovery after link goes down. APARTXT NA02183 = "recv: connection timeout" message appears on interface statistics screen when x25 interfaces are present APARTXT NA02121 = Doing translational (SRTB) bridging from token ring to frame relay DLCI that is configured as translational bridge. There are other DLCIs that are configured for source route bridge. In this case, specifically routed frames destined for the TB DLCI are actually sent as source routed frames. Sessions can not be established. APARTXT NA02160 = lanwrite message queue full lanwrite process blocked station transmit queue full DLSw buffer pool high utilization degraded DLSw performance APARTXT NA02215 = The analyst was always caching the source netbios name regardless of what the netbios command was (some netbios commands do not have valid names). This would fill up the netbios reachability database with lots of netbios name number_1 values, which are useless. Looking at the netbios command before caching the names will prevent this from occurring. APARTXT NA02170 = TB is passing Discovery SAP (FC) to DLS LLC which causes LLC to lose MBUFs until the system MBUF pool is depleted. Problem only occurs when using Transparent Bridge. APARTXT NA02175 = smux.pppd dump when ibmpppLinkControlTable queries are more than 16 ports. This causes system utilization to go to 100% Each time an snmp ppp query is done, smux.pppd dumps. APARTXT NA02292 = poor messages and incomplete error recovery from errors on writex() and ioctl(). APARTXT NA02176 = can go into a self initiated re-boot when bridging traffic that contains NetBios and SNA traffic through translatio nal bridging from T.R. to E.net if a slow(9600 in test case) serial link is involved. The following was the test/reproducibl e configuration. __ ____ ____ _____ Servers / |6611| ____ |6611| |6611| SNA | |--|TL |--| |--|TP |---//--|SR |--- NetBios _/ |Bri | |Bri | |Bri | |____| |DLS | |DLS | / |PC | |____| |____|--| |--|Cli| / |ent| |___| In the test case, the PC client tries to copy a file on the NetBios server(in the test case, a PS2) and the file size is 80K. In most cases the 6611 doing the translational bridging will fail and re-boot. Short messages do not appear to cause the problem and if the serial link is replaced with a high speed( 500K) link, the problem did not occur. The problem was al so not inducible by rapid page browsing in and SNA session. APARTXT NA02178 = CfgDaemon is attempting to refresh invalid component sap. This is causing SYSMON to reject the command and if it is recieved at the same time that CfgDaemon tries to start the interface scripts, SYSMON loses those requests because they are being read in with the invalid component. This is a problem with the IPX script handler for ipx sap filters. This code is no longer used. APARTXT NA02615 = analyst is hung (not processing frames) APARTXT NA02224 = fastpath command tftp does not work. APARTXT NA02211 = Getting SDL8053 errors and the sdlc port is not coming up. Start ed occuring when migrated from v1r2 to NP00601 using NP99917. APARTXT NA02212 = IP route limit on cards is 2817 routes. Increase limit for new cards to allow 4096 IP routes. Old cards will continue to support 2817 due to DRAM constraints. APARTXT NA02218 = ifconfig {ifname} down doesn't work right for scram so when an interface and protocol is configured but the interface is disabled, we must prevent the interface script from being run. APARTXT NA02225 = After Customer had WAN outage, some DLS SNA sessions were hung in RemDscPnd state, State 10 . This state only occurred on one side of the DLS partners. When workstations tried to login even after WAN restored, logins were rejected because RemDscPnd had not cleared for these workstations' MAC addresses. APARTXT NA02228 = Rinstall gives a error message "shift: bad number" if there is a blank line in the control file. This apar referes to rinstall at the 383 level. Below is a list of problems with making rinstall work at this level. 1) customer must define a host name to ip address for both the server and the client(s). On the 6611 this can be done on the config tool, node management, remote hosts 2) there is a apar na01369 against rinstall, fixed in 385, the main fix from this apar can be put onto a 383 machine APARTXT NA02230 = stopped communicating, and the error log is filled with system running out of paging space entries. APARTXT NA02299 = message: "haltimg circuit" in pd_sysmon.trc identifying an APPN circuit. Accompanying this will be a message indicating that an ioctl(DLC_EXIT_LBUSY) failed. STOP_SYMPTOM APARTXT NA02238 = After NP00601 + FX60103 Activated, customer has DLS WAN Connections that are stuck in EXIT'N state and new request for partners go in EXIT'N state. "dlstools p" shows that the analyst process is missing from the active process list. Analyst had exitted because of reaching full WAN database, "dlstools dbop -det 9" shows current number of records is 200 and max is 200. DLS apparently is not doing needed connection cleanup. Because analyst is gone, additional DLS partners cannot be established. APARTXT NA02303 = Make sure time stamps now exist in pd_x25d.out and that nothing else breaks. APARTXT NA02253 = GATED taking up CPU cycles in a multiple area config. 6611 with OSPF/PPP over F/R to a 2210 using point-to-multipoint. Problem: When more than one router is advertising a stub net and the 6611 is acting as an Area Border Router, the 6611 will needlesly regenerate a summary for the stub net advertised by more than one router whenever an SPF calculation is performed. While the correct route is installed, network bandwidth and router cycles are consumed. *Customer Situation* With 2210 and point-to-multipoint over frame relay, the 2210 always advertises it's local interface with a cost of zero. Conversely, 6611 implements logical point-to-point over frame relay and always advertises the destination networks to which it is attached. So, in a topology where you have a 6611 using logical point to point over F/R to a 2210 using point to multipoint, the problem is multiplied. APARTXT NA02254 = Missing summary routes in UPS network where 3 areas are being used. Only noticed on one of the two routers using a 3rd area. The other 3 area router is a backup to this one and would not have produced the problem unless it became primary. Problem is intermittent, once a week but more often recently... Smact restart gated will restore operation for another indeterminant cycle. APARTXT NA02317 = Fix framerelay dlci view for multiple IP addrs per DLCI STOP_SYMPTOM START_TEST Issue fr dlci v int for framerelay interface that has multiple IP addresses for the same DLCI APARTXT NA02318 = Fix trace status for ip trace APARTXT NA02259 = passes through XID on T/R stating maxout 7 is being used when in reality a hard coded value of 2 is used. This causes a performance throughput problem when the workstation is configured for a maxin of 7. APARTXT NA02260 = everybody on the ring, they in turn forward the packet back to the 6611. As a result, a broadcast storm on the ring. storm. For instance, if ws1 (9.180.145.3 w/ mask ff.ff.fc.0), ws2 (9.180.148.63 w/ mask ff.ff.fc.0) and a 6611 (9.180.144.1 w/ ff.ff.f8) on the same ring, both ws1 and ws2 had a default route point to 6611, when ws1 tried to reach ws2, the 6611 should tell the ws1 redirect the traffic to ws2 directly, but 6611 instead, using all "1" as the destination mac address and forwarding the icmp packet on ring which then was picked up by APARTXT NA02304 = Software primitive tftp does not work APARTXT NA02305 = With connection to 2210, 6611 X.25 link recovery was not successful when cable was pulled then replugged. APARTXT NA02261 = Pacing on frame relay does not take into account, the number of saps and rips that are actually being broadcast. It doesn't consider Split Horizon or filtering that is configured. It just calculates based on the number of rips and saps in the tables. The result is that when big tables primarily learned from interfaces with split horizon cfgd are broadcast on. the rips and saps are bunched up in the first few pace intervals. With this fix the actual number of saps and rips to be transmitted is used to calculate the packet quantity per interval, so the packets are spread out over the whole interval. APARTXT NA02263 = On recovery of PPP link, PPP establishes connection immediately but GATED / OSPF / IP, delay 75 seconds before IP makes the route available. Delay previously required because of problem with route flooding. Code was introduced earlier to resolve flooding problem and delay must now be removed. APARTXT NA02269 = Losing ability to start new DLSw sessions. Problem believed triggered by 2210 patch 44. 2210 closes a broken or fail-to- establish session in a way that causes 6611 not to remove dead entries from the message queue data base 9. Queues remaining have entries containing "NO_IP...". When database fills, with 200 of these entries, the analyst exits and no more sessions can be started with anyone. Problem also agravated by 2210 not haveing a DLSw partner defined as this causes the sessions to not establish. APARTXT NA02278 = Customer running NP00601 with FX60105. They start IPX traces and are unable to stop them so they grow without bounds. * We noticed /etc/fuser is not in this level of code APARTXT NA02311 = If the router is brought down ungracefully(power switch, reset button, power outage) on 6611 models 175, 145, or 12x, when router is brought back up the date has moved one day forward. APARTXT NA02314 = The button under transparent bridging to either filter or forward duplicate addresses has the inverse meaning. That is filter forwards and forward filters APARTXT NA02315 = Scram is dying because a stop interface is being issued by monintr to an interface that does not have a protocol address configured. The fix is to remove the check_kernel_state routine in monintr.c. SCRAM still shouldn't die under this condition but because the design effort required to fix this in SCRAM is significant and the check in monintr is redundant. APARTXT NA02313 = A MS DLS PC on an ethernet connection to 6611 has problems establishing a DLS session for SNA. DLS uses a test command to facilitate setting up its link station. MS DLS sends an XID command and refuses to answer the test command. The 6611 refuses to pass the XID command to the intended partner, so there is a deadlock situation. The architecture says that, both the Test command and the XID should be responded to immediately. Similar problem was fixed for Token Ring terminals already. APARTXT NA02322 = DLS does not respond with name recongized to second name query if second name query is within 10 seconds of first query. APARTXT NA02504 = Activating a prior level without the clock fix (22046) causes the clock to read 2/25/30. APARTXT NA02616 = Inventory changes for fx60109, v1r3_p383fx APARTXT NA02360 = no LLC_WRITE trace entry for ethernet APARTXT NA02329 = Software update apply FX60108 fails with message that FX60108 is not in transfer directory, but it really is there. Apply from sysman works. There is a problem with the fast path command not creating a new table of contents if one already exists. APARTXT NA02331 = /2210 when the serail link goes down then recovers the 6611 is not downloading the routes to the adapter. See Acee or Phuong. APARTXT NA02368 = Outbound filter order table is not be set up correctectly This might cause problems in filtering. APARTXT NA02369 = FIXES PROBLEM 1 BELOW ONLY PRIOR TO R4AP PLUS 1. outbound (maybe inbound) transparent bridge sliding window filters on frame relay ports do not work A work around for this is to use the Data starting point in the filter as if it were the MAC starting point and DO NOT USE the MAC starting point 2. It is possible that all window filters do not work. A variable that indicated which filter order objects to use (box lvl or port lvl) was confused. By chance r4ap+ worked, but p620 did not. APARTXT NA02364 = The symptoms of this problem are varied and include the possiblity of not being able to ping the broadcast address. Other symptoms include loss of contact with formerly reachable nodes. The problem usually is characterized by the Frame Relay arp table looking strange with multiple entries for identical IP addresses, no sometimes no broadcast entry at the end of the table and aiNumIp looking strange in comparison to the table contents. We found that the problem could be introduced when multiple DLCI dele tes were processed as a result of receiving an LMI message which indicate d that more than 1 DLCI was deleted or went inactive. Although our code correctly decremented the total number of entries in our Frame Relay arp table, it did not fully move all entries backwards as the table was shrunk in processing multiple deletes. APARTXT NA02366 = When a PPP link goes Up/Down, a garbage ip addr. 186.223.202.17 appears in the neighbor table due to a mishandling of the LSA structure. Gated keeps logging find_nh_entry FAILED on that addr This problem only occurs at FX60105 and follow-on PTFs. APARTXT NA02371 = sysmon filled with BAD write state 0 ?->? Local=(xxxxxxxxxx,f0) lanwrite.c--2190>>BAD write Sap f0 is now invalid, sysmon and error log fill with these messages, data link switch can no longer get anything through this adapter, but adapter is up, and you can ping through it. APARTXT NA02384 = Schedule config changed caused config deamon to dump. APARTXT NA02404 = When Scram somehow could not read nap_message sent from frame relay, it then closed the nap socket. Later on when Frame Relay sends nap messages to scram indicate that the DLCIs are UP, the message are discarded due to the closed pipe. As a consequence, the kernel interface structures were not updated, ospf therefore did not establish the ospf neighborhood. APARTXT NA02425 = LAN8041 message in the error log incorrect. Should say that : No Response to IFrame, Retry's Exhausted, Dropping Link Station. APARTXT NA02509 = If a single router attempts to multiple originate OSPF type 5 (ASE) LSAs for the same network but different mask, one of them must be bypassed since we support RFC 1247 rather than RFC 1583. Under certain conditions, this can cause problems for the other exported routes. This defect rectifies this problem. APARTXT NA02506 = The problem is that lanwrite issues a FLOW CONTROL ioctl for a link station that has just gone down, thus the ioctl fails. Because of this failure, lanwrite calls HaltCircuitNow() which sends a HALTLS_NOW Msg over the WAN and then issues a DLC_HALT ioctl. Well, because the link station has already gone down this second ioctl fails also. And because it fails, the conversation state is NOT changed (which just happens to be REMDISCPEND in this case). Because the HALTLS_NOW was sent, we will never get a LS_HALTED Msg back, and thus we will remain in REMDISCPEND for the rest of eternity. APARTXT NA02493 = Getting underrun errors when using dual port ethernet cards and transferring IP data port-to-port when segmenting is being used. The problem can be created by pinging with a 1500 byte ping frame through the port-to-port of the card into a network that is defined for 1492 frame size. Pinging with more than 4000 bytes will cause the error in almost every instance. APARTXT NA02528 = SCRAM stops receiving NAP alert messages after reporting "No buffer available" hence DLCI up/down status is not received and OSPF neighbors are not established. (FUJI bank problem) APARTXT NA02545 = The cost-reduced ethernet adapters have significant number of underruns on transmits, especially during high traffic with large frames. APARTXT NA02544 = DLS fails to free buffers when more than 1000 sessions are simultaneously in the session establishment state. Each additional session est. attempt will cause a buffer release failure. The condition is cumulative until DLS is restarted. APARTXT NA02546 = If 6611 sdlc port using a modem goes down and then back up the 6611 will take a dump and then reboot. APARTXT NA02551 = On error, ospfquery core dumps. Also ospfquery is dependent on smux.r66d being active and doesn't need to be. APARTXT NA02637 = first time customer logs in with default id 6611c, integrity group requires we force a password change. APARTXT NA02622 = Move some data from SRAM to DRAM due to depletion of bcbs. APARTXT NA02598 = Extraneous messages when rejecting PTF from fastpath APARTXT NA02552 = Thru SYSMGR, configuring the ipx network number in hexdecimal format got a failure return code indicated that the value has to be in hex. value which it actually is. APARTXT NA02555 = fast path command appn set -mode_name COS_number mode_name fails with error "appncfg not found" APARTXT NA02561 = About every 2 weeks router cannot support dls connection to a specific netbios server. Server is configured with a default router. APARTXT NA02564 = Router running FX60113 is collecting RmtDscPnd and HltRpAkPd states. Sessions cannot be established after such states have been hung for all the paths available. Problem occurs between IBM andIBM and IBM and BayNetworks routers. APARTXT NA02568 = Routes in holddown (e.g., RIP) are still advertised when exported into OSPF. APARTXT NA02587 = Enhancement for ospf_sock APARTXT NA02588 = Since SCRAM no longer flushes routes on detection of a new interface (perf. improvement) a test program is required to allow routes to be flushed in the event something get's messed up (hopefully we won't have to use this). The new program also allows one to add or delete an IP route from the card adapter tables. APARTXT NA02623 = Makefile cannot be common for v1r3 and v1r3_p383fx since rawstat is not supported in these releases. APARTXT NA02659 = v1r3_p383fx sdlc SDL.ext source code was not in CMVC prior to this defect. Now SDL.ext will be built through normal build process rather than checking in a binary SDL.ext. APARTXT NA02603 = On the TEST Command all routes broadcast response, DLS is settin g the RIF field in the route it saves for connection to the MAC address. APARTXT NA02612 = trcfmt gives incorrect output when formatting appn trace records. It indicates invalid pras format. APARTXT NA02638 = Internal Enhancements for NP00642 APARTXT NA02643 = Internal Enhancements for NP00602 APARTXT NA02658 = Internal Enhancements for NP00602 APARTXT NA01379 = APPN station hangs if it uses a DLSw wan connection that drops while the station is in xid exchange. APARTXT NA01500 = STop appn and restart it via smact restart appn. Make sure there are no entries int he error log which says something to this effect: "Pid xxxxx failed." (and then something else) APARTXT NA01905 = trs data base out of sync - sessions not started APARTXT NA01942 = see description APARTXT NA02169 = WIth 6611 appn attached to a ncp and ncp to vtam, with a network node to network node realtionship, if the vtam is recycled, but the ncp does not go down, thus the TG (LLC connection with ncp does not go down), when vtam comes back up, and send 6611 a non activation xid, indicating cp to cp sessions are now supported, appn CS does not process this correctly. APPN TRS continues to show the status of the tg with vtam as "not supporting cp to cp sessions" APARTXT NA02538 = On a link bring up, after xid exchange, and bind for a cp to cp session, each node sends a attach for the cp capabilities TP, if the fmh5 attach leaves off the trailing fields of length 0, 6611 sends fmh7 with no sense code. This is incorrect, 6611 should accept this type of attach. ENDSET COMPID FOR PTF NP00602 = 564801600,130 PRODID FOR PTF NP00602 = 5648016,Multiprotocol Network Program PREREQ FOR NP00602 = NP00383 NP00600 NP00601 ENDSET COREQ FOR NP00602 = NONE ENDSET SUP FOR NP00602 = NONE ENDSET IFREQ FOR NP00602 = NONE ENDSET MEMO TO USERS = +--------------------------------------------------------------------+ | | | MEMO FOR NP00602 | | 602 01 | | | +--------------------------------------------------------------------+ CONTENTS OF THIS MEMO _____________________ o Prerequisites o Installation instructions (New Service Process) for NP00602 o Change in Engineering PTF Service o Reject Processing PREREQUISITES _____________ PTF NP00602 requires MPNP V1R3 at PTF NP00383 code level. This code level can be achieved by one of the following: o Applying NP00383 to a base V1R3 system o Applying NP99915 to a prior release (NP99915 is V1R3 with NP00383). o Applying NP00383 on a NP00380 ( or NP00381) system. NOTE: If you are starting at V1R3 base level, you must receive and apply NP00383 prior to using NP00602. DO NOT apply NP00383 and NP00602 in the same step. Customers already at PTF level NP00600 or NP00601 will not be required to reject NP00600 or NP00601, they can install PTF NP00602 directly on top of NP00600. PTF INSTALL INSTRUCTIONS FOR NP00602 (NEW SERVICE PROCESS) __________________________________________________________ To apply NP00602, first load the image in the transfer directory, then use "Apply Software Updates" to select NP00602 from the available PTFs. Unlike updates in the old service process, the user is no longer prompted to commit applied updates or to reject applied EPTFs. The new service process separates the action of code application and actual code use (activation). Therefore, the apply step does not cause a reboot (IPL) since the running code has not changed. The activation of the updates is achieved via the "Activate Applied Updates" function. When updates are activated, a reboot (IPL) occurs and the selected updates become the running code. Selecting a different running level is done by activating a new level (that has been previously applied). Therefore, code updates must be activated after they are applied. This new activation step allows the selection a PTF level and an associated EPTF level. (If you have no EPTFs yet, be sure to select "NONE" on the EPTF selection screen). CHANGE IN ENGINEERING PTF (EPTF) SERVICE: _________________________________________ Once NP00602 has been activated, the selector screen for EPTFs will limit your choice to a single EPTF (or "NONE"). If there is an implicit prerequisite relationship among the EPTF selected and any applied EPTFs,then those prerequisite EPTFs will be activated automatically. If you are running with the new service process prior to NP00600, you should select only ONE of the EPTFs listed in your selector, even if more than one selection is allowed. Selecting more than ONE EPTF may result is a combination that was never intended to operate together. EPTFs intended to operate together have a prerequisite relationship that identifies the correct hierarchical order. REJECT PROCESSING _________________ Unlike the old service process, selecting another version of running code is done via "activate" rather than via "reject". Activating at a different code level does not remove the other updates, it just does not include them as part of the running code. Therefore, one can switch back and forth among various service levels by activating the desired level. The reject process is the method used to remove (erase) the code update from the machine. After reject, that code is no longer available on the machine unless the PTF or EPTF is loaded and applied again. Any PTF or EPTF that is not active can be rejected. Rejecting an PTF that is a prereq of another PTF will also cause that PTF to be rejected. Also, when an PTF has associated EPTFs, all those EPTFs will be rejected (erased) when the PTF is rejected. To reject a PTF that is currently active, you must first activate at a level that does not include that PTF. END OF MEMO - NP00602 ENDSET LABELTXT Selective Fix Package For use on MPNP V1, R3.0 only ENDSET ***************************************************